Only available for Logged-in member. Please login or register to access this information.

Or use the Temporary User that we have provided to you via email.

expiry time

Manual for WSLRW-SMT01 | FW2

Normally Stock

Replaced by

Item codes	FW Released Date	Changes Information
WSLRW-SMT-01	30/06/2023	1. Add regions: AS923-2, AS923-3, AS923-1-Japan; 2. Enable to change the frequency channel in band EU868 IN865 RU864 KR920 AS923 AU915 US915 and default 1; 3. Add Heartbeat event; 4. Payload updates; 5. Using new sensor → set SOIL_MOISTURE_FACTOR (for manufacturer)

1
QUICK INSTALLATION GUIDE

1.1 Introduction

WSLRW-SMT is LoRaWAN Soil Moisture Sensor, can be used to measure the Soil Moisture, Fertilizer and Soil Erosion, too. It is powered by 02 x AA-type batteries and can last up to 10 years. The Moisture sensor utillize the Frequency Domain measuring technique to deliver high accuracy and stable measurment of Soil moisture. The Moisture value is not affected by fertilizer content and temperature like other simple Capacitance Moisture Sensor on the market. The sensor will transmit data in kilometers distance to LoRaWAN gateway, any brand on the market. The typical applications are Smart farm, Smart Agriculture, Automatic Irrigation System, Soil Qualtiy Measurement, Soil Erosion Monitoring...

How the sensor connect to system?

Below is the LoRaWAN system architecture

System components:

The end nodes are LoRaWAN Sensors or Actuators;
The Gateways are LoRaWAN Gateway or Base Station;
The Network Server can be SAAS or On-premise server;
The Application Server is the destination software users want to utilize the data from/ to LoRaWAN sensors/ actuators.

How to set up the LoRaWAN system? Please follow these steps:

Adding the Gateways to a Network server. Please refer to the manual of Gateway and Network Server software;
Adding the End nodes to the Network Server;
Configure the callback or data forwarding from the Network Server to the Application Software by MQTT or HTTPS. Please refer to the manual of the Network Server.
Once the payload is on the Application server, decode data from Payload. Please check Section 1.9 for the Payload document.

1.2 Application Notes

For Applications

Flood Monitoring, Infrastructure Monitoring, Smart Irrigation

Notes

FDR sensors need to have good contact with the medium they measure with no air gaps;
Water content in soil must be higher than 20% for proper measurement;
Prevent direct sunlight on sensor housing for temperature not increase more than 50℃.

1.3 When does device send Uplink messages?

The device will send uplink messages in the following cases:

Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device.

Case 2: Then, in every interval time (pre-configured), for example, 10 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...

To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.

Case 3: If ALARM_ENABLED=1, the device will send ALARM message immediately when device switches from Normal state to Alarm state. It will repeat sending ALARM messages in predefined ALARM_PERIOD time interval if the Alarm state still exist.

Case 4: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s.

Case 5: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.

Case 6: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration.

1.4 Default Configuration

This SMT soil sensor has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Below are some configuration parameters that store in the flash memory of the wireless transmitter. Please check Payload document for more information.

1.5 Battery/ Power Supply

The Device uses below batteries:

Battery type: Primary battery
Battery size and Voltage: AA 1.5 VDC
Number of batteries: 02
Recommended batteries: Energizer® L91 or equivalent from Duracell;

Battery Installation

Open the housing of the sensor by unscrewing 2 hexagon screws and insert the batteries into the battery holder

Re-install the housing, pay attention to put the PCB edge into the middle guiding slot of the box inside as shown below)

Note:

Please take note on the polarity of the battery.

Understanding the battery levels:

Level 3 (4 bars): battery energy is 60-99%
Level 2 (3 bars): battery energy is 30-60%
Level 1 (2 bars): battery energy is 10-30%
Level 0 (1 bar): battery energy is 0-10%

1.6 What's in the Package?

1.7 Guide for Quick Test

With the default configuration, the device can be connected quickly to the Network Server by the following steps.

Step 1: Prepare the values of communication settings

Frequency zone: Most of the sensor was configured the frequency zone to suit customer application before delivery

DevEUI: Get the DevEUI on the product nameplate

AppEUI Default value: 010203040506070809

AppKey Default value: 0102030405060708090A0B0C0D0E0F10

Activation Mode: OTAA with local join server

Network Mode: Public

LoraWAN Protocol: version1.0.3

Class: A for sensor; C for actuator

If current basic common settings do not match with your region, network server/application, follow below instruction to change them as below:

For changing other settings, please refer to Section 3.2 Sensor configuration to change the other settings

Step 2: Register the device on the LoRaWAN network server

Input the above settings on your device registration page of the network server.

Note: Different network server software will have different device registration processes. Please refer to the manual of the network server software used for more details.

Please visit the below Section 1.10 to get the instructions for adding the LoRaWAN sensors to some common network servers such as Actility, TTN...

Step 3: Install the batteries to the device OR do power wiring and supply external power to the device if applicable

Please refer to Section 1.5 as above for instructions on battery installation OR for instructions to do power wiring and supply external power to the the device if applicable

After installing the battery in 60 seconds, the first data packet will be sent to the LoRaWAN gateway. After receiving the first data packet, the time of another packet depends on the value of the parameter: cycle_send_data. Additionally, you can use a magnet key to touch the magnetic switch point on the housing within 1 second to initiate force packet of the device to send data instantly and the LEDs on the housing will be lit with SKY BLUE color.

Step 4: Decode the payload of receiving package

Please refer to Section 1.9 Payload Document and Configuration Tables for details of decoding the receiving packet to get the measured values.

If the device has local display, measured values are shown on the local display

1.8 Installation

Dimension Drawings and Installation Gallery (Photos and Videos)

WSLRW-SMT_en_5.jpg

WSLRW-SMT_en_3.jpg

1/4

Please follow the checklist below for a successful installation:

1. Have you studied the dimensions of the device as above drawings?

2. Have you tested and make sure the device have been connected successfully as Section "1.7 Guide for Quick Test" above?

3. Have the device been configured properly as per Section 3.2 below?

4. Have the device been calibrated or validated as per Section 3.3 below?

5. Then you can start to install the device at site. Please check the following Installation Notes for Sensor Part (if available) before installation.

Installation Notes for Sensor Part (if available)

General Notes:

FDR sensors need to have good contact with the medium they measure with no air gaps. All the metal electrodes must be inserted into the soil during measurement;
Avoid direct sunlight on the sensor, which will cause excessive temperature;
Do not bend the metal electrodes violently, do not pull the sensor lead wire with force, and do not beat or violently impact the sensor;
The protection grade of the sensor is IP68, which can soak the sensor in water;
Since the electrode directly measures the conductivity of the soluble salt ions in the soil, the soil volumetric water content must be higher than about 20% when the soluble ions in the soil can accurately reflect the conductivity of the soil. In the long-term observation, the measured value after irrigation or rainfall is closer to the true level. If you are performing a quick test, you can water the soil to be tested first, and perform the measurement after the water is fully penetrated;
The sensor should be protected from severe vibration and impact, let alone knocked with hard objects.

Soil Surface Measurement:

- Clean the soil surface by removing the debris, and vegetation...

- Insert the electrodes completely in the soil, as in the below picture;

- If you measure on a hard surface, you should drill a hole first (the hole diameter should be smaller than the probe diameter), then insert it into the soil and compact the soil before measuring;

Multi-layer Measurement

- Make a soil profile in the vertical direction, slightly deeper than the installation depth of the bottommost sensor, between 20cm and 50cm in diameter;

- Insert the probes horizontally at different layers of soil;

- After the installation is completed, the excavated soil is backfilled in order, layered, and compacted, and horizontal installation is guaranteed.

Installation Guide for Main Device

Check the Location for the best RF Signal

Make sure the site is good enough for RF signal transmission.

Tip: To maximize the transmission distance, the ideal condition is Line-of-sight (LOS) between the LoRaWAN sensor and the Gateway. In real life, there may be no LOS condition. However, the LoRaWAN sensor still communicates with the Gateway, but the distance will be reduced significantly.

DO NOT install the wireless sensor or its antenna inside a completed metallic box or housing because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.

Mounting the Device on the Wall or Pole

Mount the sensor onto a wall by the mounting bracket as below pictures

1.9 Payload Document and Configuration Tables

Please click below button for:

Payload decoding of Uplink messages;
Payload encoding of Downlink messages;
Configuration Tables of device.

Note:

If the content of below web payload, memory map, and sample decoder could not be copied, please install the extension of "Enable Copy Paste - E.C.P" for Microsoft Edge and for Google Chrome.

Payload Document and Configuration Table

Sample Decoder

Decoding Examples

1.10 How to connect device to Back-end/ Network Server/ Coordinator

Please find below the examples of adding Daviteq's LoRaWAN sensor to the following Network servers:

ThingPark Community (of Actility);
Things Stack (of The Things Network).

You can use the similar methods to add LoRaWAN sensors to other Network Server.

1. THINGPARK COMMUNITY (ACTILITY) NETWORK SERVER

1.1. Example to add the Tektelic LoraWAN gateway Model T0005204 to ThingPark Enterprise SaaS Community

1. Log in to your ThingPark Enterprise account via the link: https://community.thingpark.io/tpe/

2. Browse on the left panel to Base Stations, click the drop-down menu, then click Create.

3. Select the base station’s Tektelic.

※ If you do not find the Tektelic, click View More Manufacturers.

4. On the following screen, select the Model: Micro 8-channels from the drop-down list.

5. Fill the form as below table:

Input exactly as above Input field column, except Name field is user-defined and is different from the existing base station name on the network server.

After filling the registration form, click CREATE to complete adding the base station to the network server.

1.2. Add Daviteq's LoRaWAN devices to ThingPark Enterprise SaaS Community

ThingPark Enterprise supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server that is programmed at the factory.

Manual provisioning of OTAA devices using a local Join Server. To learn more, see Activation modes.

1. At left panel of the screen of the Thingpark GUI, click Devices > Create from the dashboard.

2. Select the Generic supported by your device on your screen.

3. Select the Model of LoRanWAN 1.0.3 revA - class A with correct frequency plan

4. Fill the form as below table:

In addition to filling out the form, the option to select the connection between ThingPark and Daviteq application (Globiots).

After filling out the registration form, please click CREATE to add devices to the network server.

1.3. Send a downlink frame from Thingpark Network Server to the device

Follow the below steps to send the downlink frame from Thingpark Network Server to the device:

This functionality is active only when a connection is associated to the device (one of the color codes with a green bullet).

1. Navigate to the left panel, click the Devices' drop-down menu, then click List.

2. Browse the right side in the Devices, click the icon of the device and click Send Downlink.

3. Input the downlink code to the Payload field and input 1 to the Port field, and then click Validate.

The downlink data is added to the device downlink queue in network server. The downlink is sent after the network server receive an uplink from the device.

2. THINGS STACK (THE THINGS NETWORK) NETWORK SERVER

2.1. Add Sentrius LoraWAN gateway (Model RG19) to The things Stack network server

1. Log in to you’re The Things Stack account

2. Click the tab Gateways, click Add gateway button

3. Fill out the form as below table:

Input exactly as above Input column, except the Gateway Name field and the Gateway ID field is user-defined. It is different from the existing gateway name and gateway ID on the network server.

After filling the registration form, click Create gateway to complete adding the base station to the network server.

2.2. Add Daviteq's LoRaWAN device to The Things Stack network server

The Things Stack supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server programmed at the factory.

1. Browse on the top panel, click the tab Application, and click Add application button to create an application

2. Fill in the information fields as user-defined, then select Create application

3. After the application is created successfully, select Add end device to register end device (LoRaWAN sensor)

4. Fill out the form as below table:

After filling out the registration form, please click the Register end device button to add the device to the network server.

2.3. Send a downlink frame from The Things Stack Network Server to the device

1. Select the device to send downlink

2. Input 1 to the FPort and input the downlink data in the payload field, and then tick Confirmed downlink and click Schedule downlink.

2
MAINTENANCE

2.1 Troubleshooting

Please find below steps to identify the problems from Communication Part or Sensor Part:

* If the device cannot connect to the Gateway or System or Co-ordinator at the first time, it is the Communication Problem;

* If the device status like battery, RSSI level, data status or other communication is normal, but the measured values are not updated or wrong, it would be the problems of Sensor part;

* If the data coming to gateway, system or co-ordinator is not frequently as expected, the problem would be Communication.

Please refer below the troubleshooting guide for Communication and Sensor Part.

Troubleshooting for Communication

Troubleshooting for Sensor Part (if available)

1. The measured value is not within the expected value

1.1 The soil is not compact: make sure the soil is compact and there are no air gaps between the soil and electrodes

1.2 The soil is special Calibrate or adjust the reading values on software or reading device based on the actual values of that soil;

1.3 The sensor was spoiled: please consult the manufacturer for a warranty or replacement.

2. The measured values of EC, Salinity, and NPK are always zero or near zero (only applied for SMT-07)

2.1 The soil moisture is too low, less than 20%. Therefore the circuit cannot measure the electrical conductivity of the soil: watering the soil and/or keep holding the last values of EC, Salinity, and NPK in the Software system or reading device;

2.2 The sensor was spoiled: please consult the manufacturer for a warranty or replacement.

3. HW_Error = 1

3.1 Loosed connection of sensor probe and wireless transmitter: check the sensor cable and connector;

3.2 The sensor probe got a problem: please consult the manufacturer for a warranty or replacement.

2.2 Maintenance

Maintenance for Main device

There is no requirement for maintenance of the Hardware of LoRaWAN Device except:

1. The battery needs to be replaced. Please check the battery status via uplink messages;

Note: When the battery indicator shows only one bar (or 10% remaining capacity), please arrange to replace the battery with a new one as soon as possible. If not, the battery will drain completely, and the resulting chemical leakage can cause severe problems with the electronic circuit board.

2. Sensor, please refer to the maintenance section of the sensor document.

Maintenance for Sensor part (if available)

The SMT soil sensor is a maintenance-free sensor.

3
ADVANCED GUIDE

3.1 Principle of Operation

Principle of Operation for device WSLRW-SMT01 | FW 2

Daviteq LoraWAN 2in1 Soil Moisture (SMT01) Sensor comprises 02 parts linked internally:

• The Daviteq LoraWAN wireless transmitter

• The Daviteq 2in1 Soil Moisture (SMT01) module

What are the primary output values?

• TEMPERATURE: Soil temperature value, unit of oC. This parameter equals TEMPERATURE_X10 in the uplink payload divided by 10

• MOISTURE: Soil moisture value, unit of %RH, used for alarm. This parameter equals MOISTURE_X10 in the uplink payload divided by 10

What are the secondary output values?

Below output values are useful for device maintenance and troubleshooting.

• Battery level (%): the remaining capacity of the battery. The parameter in the payload is BATTERY_LEVEL.

Note: To get the accurate battery level indication, please configure the battery type by Downlink type 5 or via offline cable to the parameter name BATTERY_TYPE.The default type is Primary battery. For Solar powered version, please configure to Rechargeable battery type.

• Number of consecutive Alarm: The number of consecutive alarm message. This parameter in the payload is TENTATIVE3. TENTATIVE3 will be reset to 0 when previous message is alarm and current message is cyclic.

• Alarm: alarm status of the device. The parameter in the payload is ALERT_STATUS

• Sensor error: sensor working properly or not and this parameter in the payload is SENSOR_COM_ERROR

• Sensor current configurations: current main settings of the sensor and this parameter in the payload is CURRENT_CONFIGURATION

• Sensor hardware version: hardware version of the sensor and this parameter in the payload is HW_VERSION

• Sensor firmware version: firmware version of the sensor and this parameter in the payload is FW_VERSION

Principle of operation

Most of the time, the device will be in sleep mode. When the timer reaches the Measure_Period (for example, 30 minutes), it will wake up the device to start the measurement.

*** This Measure_Period will affect the energy consumption of the device.

The measurement will take a certain time to finish; it can take milliseconds or seconds to finish the measurement. This measurement time depends on sensor type, required accuracy, and other factors. Shorter measurement time, lower energy consumption, and longer battery life.

After finishing the measurement cycle, the device can read all the measured parameters. Main parameter for alarm is MOISTURE

If parameter ALARM_ENABLE = 1

Then the device will compare the main parameter with the Low Alarm Setpoint, High Alarm Setpoint and Hysterisis. For this device, Hysterisis equal zero.

After comparison, the devices will have 03 statuses:

No_Alarm;
Low_Alarm
High_Alam.

How the device send uplink message base on above 03 states?

If Device state is No_Alarm, it will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;

If Device state is changed from No_Alarm to Low_Alarm or Hi_Alarm, it will send alarm message immediately. Please check the below picture to understand the operation flow when finishing the measurement cycle:

Once alarm happened and send the first alarm message, the device will send the next alarm message in the Alarm_Period if the device is still in Alarm states (Low_Alarm or High_Alarm). Please check below picture to understand the operation flow when the Alarm timer reaches the Alarm_Period.

If parameter ALARM_ENABLE = 0

The device will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;

Please check the Payload document to understand clearly about uplink messages, downlink messages, meaning of parameters for configuration...

Principle of Operation of Sensor part (if available)

FDR (Frequency Domain Reflectometry) type sensor is mainly composed of a parallel arrangement of the metal bar as a capacitor. In which the soil acts as a dielectric, the capacitor and oscillator are composed of a high-frequency tuning circuit. The electromagnetic wave through the coaxial cable arrives at the probe, and the resonance frequency is detected by the frequency sweep circuit. The dielectric constant of the soil can be measured so that the soil water content is obtained. The dielectric constant of water is 80 F.m⁻¹ and the soil solid dielectric constant is 2∼5 F.m⁻¹; the dielectric constant of water is much bigger than soil. Therefore, the dielectric constant of soil is mainly affected by soil moisture content. Moisture content increases, the soil dielectric constant will increase accordingly, and the frequency of the electromagnetic wave propagation will change.

Besides the moisture content, the sensor also can measure the electrical conductivity of the soil and calculate the other parameters like Salinity, N, P, and K (only applied for SMT-07).

Default Configuration Parameters of Sensor part (if available)

3.2 Configuration

How to configure the device?

Sensor configuration can be configured in 02 methods:

Method 1: Configuring via Downlink messages, port 1 (default)

Method 2: Configuring via Offline cable.

Step to access configuration port: Open housing by turning counter-clockwise 2 hex screws, then remove the anti-interference shield, the configuration port as below figure:

Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.

Which Parameters are configured?

Please check Part G in Section 1.9 Payload Documents above.

Method 1: Configuration via Downlink messages

Please check the Part D & E in Section 1.9 Payload Documents above.

Method 2: Configuration by Offline Cable

Please download the Configuration Template File of this sensor to be used in Step 4 below.

Download CSV File

Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.

Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.

1. Prepare equipment and tools

The following items must be prepared for configuration.

A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install the driver at link: How to install the driver.
A Modbus configuration cable
Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)

2. Download and launch Daviteq Modbus configuration software

Click the link below to download Daviteq Modbus configuration software:

https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs

After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use.

Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:

Note: The software only runs on Microsoft Windows OS (Windows 7 and above).

3. Connect the cable and configure the sensor

Step 1:

Connect the PC to the sensor using the configuration cable.

- Use the configuration cable (Item code: TTL-LRW-USB-01).

- Connect the USB-A plug into the USB-A socket of the PC.

Step 2:

On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none

Step 3:

Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.

Step 4:

Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.

Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.

Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.

Step 5:

Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.

Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type

Note: If the sensor has SKU of WSLRWEX-PPS and hardware version 1 & 2, the sensor must be powered by batteries for configuration

Step 6:

Read the current value of the parameter with Modbus Function 3

At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.

The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.

Step 7:

Write the new setting to the parameter with Modbus Function 16

Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;
Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.

Repeat Step 6 to read the setting of the parameter for double-checking.

Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.

Only read/ write registers are allowed to write.

4. Troubleshooting

3.3 Calibration/ Validation

How to force sensor to send data for calibration/ validation (if available)

Using the magnet key, the device can be triggered to send data to the gateway immediately.

Note:

Upon transmitting the data to the gateway using the magnetic key, the timer for the transmission time interval will be reset.

The minimum time interval between two manual triggers is 15 seconds. If the interval is less than 15 seconds, data transmission will not occur.

Calibration/ Validation sensor (if available)

The Daviteq SMT Soil Sensor is pre-calibrated with standard soil before shipping. The sensors are calibrated with Air and Water for 0% and 100% moisture. Users can make further adjustments/ calibrations by changing CONSTANT_A and CONSTANT_B value in the sensor memory using their software or offline configuration tool to meet higher accuracy for their specific soil.

For SMT07 sensors, user could calibrate NPK as below:

Instructions for NPK calibration of LoRaWAN SMT07 sensor at link:

Formulas to calibrate the NPK will be integrated in application software to calculate soil's Nitrogen, Phosphorus and Kalium from soil Electrical Conductivity (EC) values. For SMT07 with Sigfox, Sub-Ghz, Other wireless connectivity and wired connectivity, the NPK calibration's instructions are similar to those for LoRaWAN sensors.

4
PRODUCT SPECIFICATIONS

4.1 Specifications

Spec

5
WARRANTY & SUPPORT

5.1 Warranty

Warranty

Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.

Free Warranty Conditions

The manufacturer undertakes to guarantee within 12 months from shipment date.
Product failed due to defects in material or workmanship.
Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).
During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.
Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.

Note: One way shipping cost to the Return center shall be paid by Customers.

Paid Warranty

The warranty period has expired.
The product is not manufactured by Daviteq.
Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.
Product damaged during shipment.
Product damaged due to faulty installation, usage, or power supply.
Product damage caused by the customer.
Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)
Product damage is caused by unauthorized treatments and modifications.

Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.

5.2 Support

Support via Help center

If you need our support for Daviteq device's installation, configuration, test, and decode, please email us at: support@daviteq.com OR input support request at link: https://forms.office.com/r/XWHbYG7yy7

Our support engineer will contact you via email or the support ticket system.

If you have any questions about the product, you can search for information on our web (https://www.iot.daviteq.com/). If you can't find the right information, please register an account and send us a request at link Contact us | Daviteq Technologies . We will respond within 24 hours.